Digital file recognition and deposit system

ABSTRACT

Systems and methods for recognizing and depositing digital files. Receive an unidentified file. Identify a target client and at least one account associated with the unidentified file. Segment the unidentified file into one or more document images. For each document image: scan the image and extract content, label the image based on its content, select an account of the target client, and deposit the labeled image in the selected account.

FIELD OF TECHNOLOGY

Aspects of the disclosure relate to digital files. Specifically, aspectsof the disclosure relate to digital image file recognition systems.

BACKGROUND OF THE DISCLOSURE

Digital files are commonly used for storing a wide variety ofinformation. Digital files can be stored with more efficiency thanphysical files. Digital files can also be transmitted across vastdistances with great speed and economy.

Important documents, forms, and images are often converted into, andeven created as, digital files. In some exemplary scenarios, suchdigital files may be transmitted to an entity by clients, or prospectiveclients, of the entity. The transmission of the digital files may servethe purpose of verification, authorization, and/or informationgathering. The transmission of the digital files may pertain to anactive, or prospective (i.e., not yet active), account. The client maytransmit the digital file over the internet, e.g., via email.

An entity may receive a large number of digital file transmissions. Inmany cases, the digital files received may be unidentified. Moreover, anindividual digital file may contain more than one document, form, orimage. The digital files may be most useful to the receiving entity wheninformation contained in the files is accurately identified and labeled,and deposited in the appropriate accounts of the correct clients. It isa challenge to accurately deposit the contents of unidentified files,especially those containing multiple items. Inaccurate identification,labeling, and/or deposit can lead to the loss of vital information.

It would be desirable, therefore, to provide systems and apparatus fordigital file recognition, disaggregation, and deposit.

SUMMARY OF THE DISCLOSURE

Aspects of the disclosure relate to an email plugin. The plugin mayinclude computer executable instructions that, when run on a processor,are configured to receive, via email attachment, an unidentified file.The unidentified file may include at least one document image on one ormore pages.

The plugin may identify a target client associated with the unidentifiedfile. The plugin may further identify at least one account linked to thetarget client.

The plugin may segment the unidentified file into the one or more pages.For each page, the plugin may search a set of document templates for amatching document template. A matching document template may be atemplate that satisfies a threshold level of similarity to the page. Theplugin may create an identifier for the page based, at least in part, onthe matching document template.

The plugin may group the one or more pages into one or more sets ofpages. Each set may include pages with matching identifiers. The pluginmay define each set of pages as a unique document image.

For each document image, the plugin may create a labeled file. A labeledfile may include the document image and a label identifying the labeledfile based, at least in part, on the matching document template. Theplugin may select an account from the at least one account fordepositing the labeled file, and deposit the labeled file in theselected account.

BRIEF DESCRIPTION OF THE DRAWINGS

The objects and advantages of the disclosure will be apparent uponconsideration of the following detailed description, taken inconjunction with the accompanying drawings, in which like referencecharacters refer to like parts throughout, and in which:

FIG. 1 shows an illustrative system in accordance with principles of thedisclosure;

FIG. 2 shows an illustrative apparatus in accordance with principles ofthe disclosure;

FIG. 3 shows an illustrative flowchart in accordance with principles ofthe disclosure; and

FIGS. 4A-4H show illustrative screenshots in accordance with principlesof the disclosure.

DETAILED DESCRIPTION OF THE DISCLOSURE

Aspects of the disclosure relate to a digital file recognition anddeposit system. The system may include computer executable instructionsrunning on a processor. The instructions may be stored in anon-transitory memory. The processor and/or the memory may be part of acomputing device, such as a smartphone, tablet, laptop computer, ordesktop computer. In some embodiments, the memory and/or processor maybe part of a remote server or cloud.

A user may access the functionality of the system via a user interface(“UI”). The UI may include a screen for display. The UI may also includevarious other input/output (“I/O”) components for receiving user inputand producing output. Exemplary I/O components may include a keyboard,mouse, touchpad, touchscreen, speakers, and other such suitable I/Ocomponents.

In some embodiments, the system may be configured to operate as an emailplugin. An email plugin may be an application designed to integratewith, or piggyback atop, an email messaging service. Examples of suchemail services include Microsoft Outlook, Gmail from Google, AOL, etc.The plugin may be displayed on a portion of the screen when the emailservice is running. In other embodiments, the system may be a softwareprogram or application that stands alone, or runs in conjunction withany other suitable service, program, or application.

The system may receive an unidentified file. The unidentified file mayinclude at least one document image. The unidentified file may beunverified as to how many, and what type(s), of document images arecontained within. A user of the system may wish to identify how manydocument images are contained in the file and what type of documentsthey represent. The user may also wish to deposit each document image inits appropriate location. Inaccurate deposit of the document images maybe detrimental to a broader system within which the system is operating.

The unidentified file may be received via email attachment. In someembodiments, the unidentified file may be received in any other suitablemanner or method. Other suitable methods may involve other digitalmessaging services, downloading from the internet or other digitalnetwork, transferring via digital memory device (e.g., USB device orhard drive), or receiving directly via an image capture device such as ascanner or camera. It is envisioned that, in certain embodiments, thesystem may be integrated with a native image capture device, for directimage capture, recognition, and deposit (e.g., a system configured torun on a computing device with a camera that can take a snapshot of anunidentified form, and directly recognize and deposit the form in theappropriate location).

The system may be configured to be operable with unidentified files ofthe following file formats: pdf (portable document format), png(portable network graphics), of/tiff (tagged image file format),jpg/jpeg (joint photographic experts group), gif (graphics interchangeformat), and pnp. In some embodiments, the system may be operable withother image formats, with text formats, or with any other suitable fileformat.

The system may identify a target client associated with the unidentifiedfile. The identification of the target client may include extractingdata about a sender of the unidentified file. For example, when theunidentified file is received via email, the email address of the senderof the email may be used to identify the target client. Any other senderdata, such as a name, address, or other suitable identification number,may also be used to identify the target client. The email address, orother sender data, may be searched against a database of possibleclients. In some embodiments, the sender data may be filtered. Forexample, if a sender email address contains a domain of an entity thatis running the system, the system may recognize that the sender is not aclient. In this scenario, the system may abort the process, look forother sender data, and/or issue an alert to the user.

In some embodiments, the system may identify the target client based ondata extracted from the document images themselves. For example, thesystem may scan the document images for a signature and extract a clientname from the signature. In other embodiments, a target client may beidentified based on a customer service session conducted with a client.For example, if a user is conducting an in-person or telephonic customerservice session with a client, any unidentified file received during thesession may be associated with the client.

The system may further identify at least one account linked to thetarget client. In some embodiments, the system conducts a search of oneor more account databases, based on the target client information, toobtain a list of all accounts associated with the target client.

In one example, a user of the system may be an associate at a financialinstitution. A target client may be a customer at the financialinstitution. The associate may receive a file attachment in an emailfrom the customer. The system may identify the customer and obtain alist of all the accounts associated with the customer at the financialinstitution. Examples of such accounts may include Trust accounts(various types including revocability, Trust under will, etc.),Investment accounts (including Management/Advisory), Custody, Estate, aswell as banking accounts such as checking, savings, CDs, IRAs, DirectDeposit Accounts (DDAs), and credit and debit card accounts. Theaccounts may include other financial accounts, or any other suitableaccount.

In some embodiments, the accounts obtained by the system may includework-in-progress (“WIP”) accounts. A WIP may be an account that iscurrently undergoing modification and/or initiation. A WIP may be aprospective account. A prospective account may include an account thatis not yet active. The account may be not yet active because it is inthe process of being set up, approved, or initialized. A WIP may, incertain embodiments, be associated with a unique identifier that isdifferent from the identifier of the account being worked on. Becauseeach WIP is generally linked to a unique account, for the purposes ofthis disclosure, the terms “WIP” and “account” may sometimes be usedinterchangeably.

In some embodiments, the system may filter the accounts. For example, incertain embodiments, only WIPs, or any other account type criterion, maybe displayed to a user. The filtering may be manual or automatic.

The system may extract the document images from the unidentified file.The extraction may include the use of optical character recognition(“OCR”). The OCR may, in some embodiments, be used to extract thecomplete content of the document images. In other embodiments, thesystem may only extract a targeted portion of the document images. Forexample, the system may scan the document images for a header, or anyother predetermined target portion or sets of portions.

The system may, for each of the document images, search a set ofdocument templates for a matching document template. A matching documenttemplate may satisfy a threshold level of similarity to the documentimage.

The system may create a labeled file. The labeled file may include thedocument image and an identifying label. The identification may bebased, at least in part, on the matching document template.

In an illustrative example, the document image may be a photo of adriver's license. The system may extract all or part of the licenseimage (this may include the overall shape, features such as a photo boxin a certain location, and/or various barcodes and identificationnumbers on the license). The system may compare the results of theextraction to a set of document templates that may include a driver'slicense template. The system may match the image to certain knowntemplates (such as a NY license, a CA license, etc.). The comparison maysatisfy a predetermined threshold, e.g., 90% of the features are amatch. The threshold may be set to account for different versions of thesame document, and/or differences due to the process, such as an unclearphoto or an inaccurate OCR extraction. In some embodiments, thethreshold may be substantially 100%, or any other suitable value.

The system may create a labeled file that associates the document imageas a “driver's license” (or any other suitable label, such as a moregeneral “form of ID,” or a more specific “NYS driver's license”). Thelabel may be appended to the file name. In some embodiments, the labelmay be stored as metadata linked to the document image.

In another exemplary embodiment, the system may initially segment theunidentified file into pages. The segmentation may be based on aretrieved file pagination. The segmentation may also be based onfeatures extracted from the file appearance, such as dark or light barsinterspersed at certain locations of the file.

The system may perform the extraction on each page. As described in thepreceding paragraphs, the extraction may employ OCR. The extraction mayutilize the entirety of each page, or, alternatively, a portion thereof.For example, a page may include a header and/or a footer. The header mayinclude a barcode and/or an alphanumeric document code. The alphanumericdocument code may also be referred to herein as a form identification(“ID”) number. The barcode and/or form ID may be unique to a specificform type.

In the current example, the system may extract the barcode and/or formID from the header of each page. The system may search a database for atemplate that matches the barcode and/or form ID. A mapping may existbetween the possible barcodes and/or form IDs, and the possible documenttypes. A document type that satisfies the mapping may satisfy thethreshold similarity. The threshold similarity may be satisfied evenwhen the rest of document image does not exactly match the documenttype. The system may create an identifier for each page based on thedocument type that satisfied the threshold similarity.

Once each page is thus identified, the system may check if multiplepages share an identifier. Multiple pages sharing an identifier mayindicate that the multiple pages belong to the same document. The systemmay group the pages into uniform sets, each set preferably containingall the pages that share an identifier. The system may stitch togetherthe pages of a multi-page set, and define each set as a unique documentimage.

In some embodiments of the system, the set of document templates mayinclude one or more contractual forms, one or more financial forms,and/or one or more identification documents. Identification documentsmay include government issued IDs (e.g., driver's license, passport,birth certificate, marriage license, etc.). Some sample financial formsthat may be supported by the system, and included in the set of documenttemplates, may include: Investment Services Agreement (ISA),Philanthropic ISA, Wire Transfer Profile (WTP), and other standard andnon-standard client provided documents. Any other suitable forms anddocuments may be supported as well.

The system may select an account, from the accounts of the targetclient, for depositing the labeled file. The selection may be based onuser input. In some embodiments, the selection may be automaticallyperformed based on a predetermined mapping between documents andaccounts.

The system may deposit the labeled file in the selected account.Depositing a file in an account may include sending the file to adedicated file repository. Sending the file to the repository mayinclude associating the file with metadata. The metadata may includedata that identifies the document type contained in the file, the targetcustomer (identified, for example, by name and/or unique customer IDnumber) associated with the file, and an account number or WIP ID linkedto the file.

In some embodiments, the system may be further configured to extractdata from the document image. The data may include content of thedocument image, such as information in data fields of the document. Thesystem may further update a database with the data. Updating thedatabase may be an important step in executing the task for which thetarget client sent the unidentified file. For example, when a customersends a document containing data pertaining to an account initializationto a financial entity, the system may enter the data into a database ofthe financial entity in order to initialize the account.

In some embodiments, an email plugin is provided. The plugin may includecomputer executable instructions that, when run on a processor, areconfigured to receive, via email attachment, an unidentified file. Theunidentified file may include at least one document image on one or morepages.

The plugin may identify a target client associated with the unidentifiedfile. The plugin may further identify at least one account linked to thetarget client.

The plugin may segment the unidentified file into the one or more pages.For each page, the plugin may search a set of document templates for amatching document template. A matching document template may be atemplate that satisfies a threshold level of similarity to the page. Theplugin may create an identifier for the page based, at least in part, onthe matching document template.

The plugin may group the one or more pages into one or more sets ofpages. Each set may include pages with matching identifiers. The pluginmay define each set of pages as a unique document image.

For each document image, the plugin may create a labeled file. A labeledfile may include the document image and a label identifying the labeledfile based, at least in part, on the matching document template. Theplugin may select an account from the at least one account fordepositing the labeled file, and deposit the labeled file in theselected account.

In some embodiments of the plugin, each page may include a header. Theheader may include a barcode and/or a document code.

In certain embodiments, satisfying a threshold level of similarity to apage may include satisfying a predetermined mapping. The mapping may mapthe set of document templates to a set of possible headers.

In some embodiments of the plugin, the computer executable instructionsmay be further configured to extract data from the document image. Theplugin may further be configured to update a database with the data.

In certain embodiments of the plugin, the set of document templates mayinclude one or more contractual forms, one or more financial forms,and/or one or more identification documents.

In some embodiments, the plugin may be configured to be operable withunidentified files of the following file formats: pdf, png, tif, jpg,jpeg, gif, and pnp.

The plugin may be further configured to support a prospective account aswell as an active account. In some embodiments, accounts supported bythe plugin may include trust, investment, custody, estate, and/orbanking accounts.

A method for digital file recognition and deposit is provided. Themethod may be performed by computer executable instructions running on aprocessor. The method may include receiving an unidentified file. Theunidentified file may include at least one document image on one or morepages.

The method may include identifying a target client associated with theunidentified file, and further identifying at least one account linkedto the target client.

The method may include segmenting the unidentified file into itsconstituent pages. For each page, the method may include searching a setof document templates for a matching document template. A matchingdocument template may satisfy a threshold level of similarity to thepage. The method may further include creating an identifier for the pagebased, at least in part, on the matching document template.

The method may include grouping the pages into one or more sets ofpages. Each set may include pages that have matching identifiers. Eachset of pages may be defined as a unique document image.

The method may include creating a labeled file for each document image.The labeled file may include the document image and a label identifyingthe labeled file. The identifying may be based, at least in part, on thematching document template. The method may include selecting an accountof the target client, and depositing the labeled file in the selectedaccount.

In some embodiments of the method, each page may include a header. Theheader may include a barcode and/or document code. In certainembodiments, satisfying a threshold level of similarity to a page mayinclude satisfying a predetermined mapping between the set of documenttemplates and the header.

The method may include extracting data from the document image. Adatabase may be updated with the data.

In some embodiments, the method may be executed as an email plugin. Insome embodiments, the unidentified file may be received as an emailattachment.

In certain embodiments of the method, the set of document templates mayinclude one or more contractual forms, one or more financial forms,and/or one or more identification documents.

In some embodiments, the at least one account of the target client mayinclude one or more of the following account types: trust, investment,custody, estate, and banking accounts. In certain embodiments, each ofthe accounts may be either an active account or a prospective account.

Apparatus and methods described herein are illustrative. Apparatus andmethods in accordance with this disclosure will now be described inconnection with the figures, which form a part hereof. The figures showillustrative features of apparatus and method steps in accordance withthe principles of this disclosure. It is understood that otherembodiments may be utilized, and that structural, functional, andprocedural modifications may be made without departing from the scopeand spirit of the present disclosure.

FIG. 1 shows an illustrative block diagram of system 100 that includescomputer 101. Computer 101 may alternatively be referred to herein as a“server” or a “computing device.” Computer 101 may be a desktop, laptop,tablet, smart phone, or any other suitable computing device.

Computer 101 may have a processor 103 for controlling the operation ofthe device and its associated components, and may include RAM 105, ROM107, input/output module 109, and a memory 115. The processor 103 mayalso execute all software running on the computer—e.g., the operatingsystem and/or voice recognition software. Other components commonly usedfor computers, such as EEPROM or Flash memory or any other suitablecomponents, may also be part of the computer 101.

The memory 115 may be comprised of any suitable permanent storagetechnology—e.g., a hard drive. The memory 115 may store softwareincluding the operating system 117 and application(s) 119 along with anydata 111 needed for the operation of the system 100. Memory 115 may alsostore videos, text, and/or audio assistance files. The videos, text,and/or audio assistance files may also be stored in cache memory, or anyother suitable memory. Alternatively, some or all of computer executableinstructions may be embodied in hardware or firmware (not shown). Thecomputer 101 may execute the instructions embodied by the software toperform various functions.

Input/output (“I/O”) module may include connectivity to a microphone,keyboard, touch screen, mouse, and/or stylus through which a user ofcomputer 101 may provide input. The input may include input relating tocursor movement. The input may be included in a transfer event or anescape event. The input/output module may also include one or morespeakers for providing audio output and a video display device forproviding textual, audio, audiovisual, and/or graphical output. Theinput and output may be related to computer application functionality.

System 100 may be connected to other systems via a local area network(LAN) interface 113.

System 100 may operate in a networked environment supporting connectionsto one or more remote computers, such as terminals 141 and 151.Terminals 141 and 151 may be personal computers or servers that includemany or all of the elements described above relative to system 100. Thenetwork connections depicted in FIG. 1 include a local area network(LAN) 125 and a wide area network (WAN) 129, but may also include othernetworks. When used in a LAN networking environment, computer 101 isconnected to LAN 125 through a LAN interface or adapter 113. When usedin a WAN networking environment, computer 101 may include a modem 127 orother means for establishing communications over WAN 129, such asInternet 131.

It will be appreciated that the network connections shown areillustrative and other means of establishing a communications linkbetween computers may be used. The existence of various well-knownprotocols such as TCP/IP, Ethernet, FTP, HTTP and the like is presumed,and the system can be operated in a client-server configuration topermit a user to retrieve web pages from a web-based server.

The web-based server may transmit data to any other suitable computersystem. The web-based server may also send computer-readableinstructions, together with the data, to any suitable computer system.The computer-readable instructions may be to store the data in cachememory, the hard drive, secondary memory, or any other suitable memory.The transmission of the data together with computer-readableinstructions may enable the computer system to quickly retrieve thedata, when needed. Because the computer system is able to quicklyretrieve the data, the web-based server may not need to stream the datato the computer system. This may be beneficial for the computer system,because the retrieval may be faster than data-streaming. Users may notbecome frustrated because they do not need to wait to run theapplications. Conventionally, streaming data requires heavy usage of theprocessor and the cache memory. If the data is stored in the computersystem's memory, retrieval of the data may not require heavy processorand cache memory usage. Any of various conventional web browsers can beused to display and manipulate retrieved data on web pages.

Additionally, application program(s) 119, which may be used by computer101, may include computer executable instructions for invoking userfunctionality related to communication, such as e-mail, Short MessageService (SMS), and voice input and speech recognition applications.Application program(s) 119 (which may be alternatively referred toherein as “plugins,” “applications,” or “apps”) may include computerexecutable instructions for invoking user functionality relatedperforming various tasks. The various tasks may be related torecognizing, labeling, indexing, disaggregating, and/or depositingfiles.

Computer 101 and/or terminals 141 and 151 may also be devices includingvarious other components, such as a battery, speaker, and/or antennas(not shown).

Terminal 151 and/or terminal 141 may be portable devices such as alaptop, cell phone, Blackberry™, tablet, smartphone, or any othersuitable device for receiving, storing, transmitting and/or displayingrelevant information. Terminals 151 and/or terminal 141 may be otherdevices. These devices may be identical to system 100 or different. Thedifferences may be related to hardware components and/or softwarecomponents.

Any information described above in connection with database 111, and anyother suitable information, may be stored in memory 115. One or more ofapplications 119 may include one or more algorithms that may be used toimplement services provided by the system, and/or any other suitabletasks.

The invention may be operational with numerous other general purpose orspecial purpose computing system environments or configurations.Examples of well-known computing systems, environments, and/orconfigurations that may be suitable for use with the invention include,but are not limited to, personal computers, server computers, hand-heldor laptop devices, tablets, mobile phones, smart phones and/or otherpersonal digital assistants (“PDAs”), multiprocessor systems,microprocessor-based systems, set top boxes, programmable consumerelectronics, network PCs, minicomputers, mainframe computers,distributed computing environments that include any of the above systemsor devices, and the like.

The invention may be described in the general context ofcomputer-executable instructions, such as program modules, beingexecuted by a computer. Generally, program modules include routines,programs, objects, components, data structures, etc., that performparticular tasks or implement particular abstract data types. Theinvention may also be practiced in distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network. In a distributed computingenvironment, program modules may be located in both local and remotecomputer storage media including memory storage devices.

FIG. 2 shows illustrative apparatus 200 that may be configured inaccordance with the principles of the disclosure. Apparatus 200 may be acomputing machine. Apparatus 200 may include one or more features of theapparatus shown in FIG. 1. Apparatus 200 may include chip module 202,which may include one or more integrated circuits, and which may includelogic configured to perform any other suitable logical operations.

Apparatus 200 may include one or more of the following components: I/Ocircuitry 204, which may include a transmitter device and a receiverdevice and may interface with fiber optic cable, coaxial cable,telephone lines, wireless devices, PHY layer hardware, a keypad/displaycontrol device or any other suitable media or devices; peripheraldevices 206, which may include counter timers, real-time timers,power-on reset generators or any other suitable peripheral devices;logical processing device 208, which may compute data structuralinformation and structural parameters of the data; and machine-readablememory 210.

Machine-readable memory 210 may be configured to store inmachine-readable data structures: machine executable instructions (whichmay be alternatively referred to herein as “computer code”),applications, signals, and/or any other suitable information or datastructures.

Components 202, 204, 206, 208 and 210 may be coupled together by asystem bus or other interconnections 212 and may be present on one ormore circuit boards such as 220. In some embodiments, the components maybe integrated into a single chip. The chip may be silicon-based.

FIG. 3 shows illustrative flowchart 300 in accordance with aspects ofthe disclosure. Flowchart 300 may show steps according to some exemplaryembodiments of the disclosure. Other embodiments may skip steps, replacesteps, and/or include additional steps. Some embodiments may includedifferent orderings of the steps.

Flowchart 300 begins with step 301. At step 301 an unidentified file isreceived, e.g., via email. Step 303 may filter the email by checking ifthe sender is an employee of the entity running the system. If thesender is an employee, the process may skip directly to the end, step331.

If the sender is not an employee, the system may identify a targetclient at step 305. Identifying a target client may include searching aclient database using an email address or any other suitable identifyinginformation. Once a target client is identified, the system may obtain alist of client accounts at step 307. In some embodiments, steps 305 and307 may be executed together.

At step 309, the system may receive an action request. An action requestmay include a user selection. A user selection may, in some embodiments,include selecting an option, such as a button, displayed on a screen.The button may be part of an email plugin displayed on the screen. Insome embodiments, the system may perform step 309 autonomously, e.g.,automatically performing the process when an email is received with anunidentified file.

At step 311, the system may select unidentified files, which may beattachments in the embodiment of flowchart 300. Selecting files mayinclude displaying the available files on a pop-up window. The availablefiles may be presented with selectable buttons, such as radio buttons,for the user to select a file for processing. In some embodiments, otherselection schema may be used. In yet other embodiments, the system mayautomatically process all the available files with minimal or no userinput.

Step 313 may include extracting metadata about the file. Step 315 mayinclude segmenting the file into pages. Step 317 may include identifyingeach page. This step may identify the content contained in the file. Thecontent may include various forms and documents. The content may alsoinclude any other content contained in a file supported by the system.In some embodiments, if the system does not recognize the identity of apage, the system identifies the page as “miscellaneous.”

Each page with a unique identifier may be defined as a document image.At step 319, the system may check if multiple pages were identified withthe same ID, which may indicate that the multiple pages are part of thesame form or document. If there are multiple pages with the same ID, thesystem may stitch them together at step 321. Stitching multiple pagestogether may include storing them together, e.g., in the same datastructure. Alternatively, stitching may include any other suitable wayfor associating the pages together, as part of the same document image.

At step 323, the system may run a multi-step process for each documentimage identified in the file. The multi-step process may includelabeling the image as a labeled file, 325, selecting an account, 327,and depositing the labeled file into the selected account, 329. When allthe documents in the file are processed, the process may end at step331.

FIGS. 4A-4H show screenshots of a system in accordance with aspects ofthe disclosure. The screenshots may show different steps of the samesession. In the particular example shown, the session includes a userusing the system to identify and deposit multiple unidentified filesreceived as attachments on a single email message. The user may, in someembodiments, prefer to use the system in conjunction with an accountopening portal, or any other suitable portal or application.

The screenshots show one exemplary embodiment. Other embodiments mayinclude less, more, and/or other features, and the features may bedisplayed in a manner other than displayed in the exemplary screenshots.

FIG. 4A shows screen 400. Screen 400 may be an email service running ona computing device. The email service may, in this exemplary embodiment,be Microsoft Outlook or similar. The attachments 406-410 may be threeunidentified files received in a particular email.

The right-hand portion of screen 400—the portion between (inclusive) thelabel “Client Details” and menu bar 404 (“WIPs in Progress”)—may be aplugin of the system configured to integrate with the email service.

The plugin may display details of a client identified as the targetclient. The details may include name, status, phone number, emailaddress, and/or other suitable information. The displayed informationmay be seen in FIG. 4A below the label “Client Details.”

The plugin may include a drop-down menu 402. Menu 402 may include a listof available actions for a user to select. User selection of an actionitem may trigger the system to execute a process, such as identifyingand depositing an attachment.

The plugin may include various bar menus, including menu 404. Menu 404may be selectable. Selecting menu 404 may trigger display of a list ofWIPs associated with the target client.

Screenshot 4B may show screen 400 after a user selected drop-down menu402 (from FIG. 4A) and the bar menu 404 (also from FIG. 4A).

WIP list 412 may include a list of WIPs obtained by the system that areassociated with the target client. Each row in list 412 may show aunique WIP. The columns in list 412 may show various informationassociated with each WIP. The information may include an account number.

Options list 414 may include available actions for user selection. Thebottom option, “Send Documents to AOP WIP” may be bold to indicate ithas been selected. Selecting the option may initiate features of thesystem shown in FIGS. 4C-4H.

FIG. 4C may a show screen 400 with pop-up window 416. Window 416 may beinitiated in response to selection of option “Send Documents to AOP WIP”included in options list 414 shown in FIG. 4B.

Window 416 may include field 418. Field 418 may include a list ofavailable unidentified files received by the system, e.g., as emailattachments. In the example of FIG. 4C, the 3 email attachments areshown with radio buttons, and the file “Philanthropic.png” is shown asselected. The image contained in the selected file may be displayed inwindow 422.

Window 416 may include field 420. Field 420 may include a selectedaccount and/or a WIP for depositing the file. In some embodiments, field420 may include a menu of selectable accounts. On other embodiments,field 420 may be a text field that a user can input with a number. Inother embodiments, the system may automatically select an account fordeposit. In still other embodiments, the system may automatically selecta suggested account, and the user may be presented a menu for the optionof selecting an account other than the suggested account.

Window 416 may also display data, or metadata, associated with theselected file. The data may include File Name, Doc Name, File Type, DocType, Domain, Medl No., and # of pages. The data may include dataextracted from the file. The data may include a label generated based onidentifying the file. Window 416 may include a submit button 424.Selecting submit button 424 may deposit the file in the selectedaccount.

FIG. 4D may show a screenshot of window 416 with a different fileselected in field 418. In the screenshot of FIG. 4D, the attachment file“WTPSample.pdf” may be selected. Field 420 in FIG. 4D may include aselected account and/or a WIP for depositing the file. Depending on thecase, the WIP may be the same or different from the WIP in field 420 ofFIG. 4C.

Window 416 in FIG. 4D may display data associated with the selectedfile. The data may be different than the data displayed in window 416shown in FIG. 4C. Window 422 may also show an image of the selectedfile. Selecting submit button 424 may deposit the selected file in theselected account. Successful deposit of the file may trigger display ofconfirmation window 426 shown in the screenshot of FIG. 4E.

FIG. 4F may show a screenshot of window 416 with a different fileselected in field 418. In the screenshot of FIG. 4F, the attachment file“ISA-MEDL.pdf” may be selected. Window 416 may display data associatedwith the selected file. The data may be different than the datadisplayed in window 416 shown in FIGS. 4C and 4D. Window 422 may alsoshow an image of the selected file.

The file selected in FIG. 4F may include two documents. The system mayrecognize that two documents are contained in the file, and alsoidentify the document type of each document. Window 416 may indicatethat 2 files are present, and show information about each. Theinformation may include a number of pages and an identified documenttype for each document.

Window 416 may also, in the scenario of FIG. 4F, be augmented to includebutton 428 which presents the option of splitting the file. Selectingbutton 428 may cause the system to split the file into the twodocuments. Selection of button 428 may also cause the system to modifythe content of window 416.

Window 416 with modified content (after selection of button 428 in FIG.4F) is shown in the screenshot of FIG. 4G. Window 418 in FIG. 4G showsthat 4 files are now available, “ISA-MEDL.pdf” having been split into“ISA.pdf” and “MF.pdf.”

Selecting submit button 424 may deposit the selected file in theselected account. Successful deposit of the file selected in FIG. 4G maytrigger display of confirmation window 430 shown in the screenshot ofFIG. 4H.

The steps of methods may be performed in an order other than the ordershown and/or described herein. Embodiments may omit steps shown and/ordescribed in connection with illustrative methods. Embodiments mayinclude steps that are neither shown nor described in connection withillustrative methods.

Illustrative method steps may be combined. For example, an illustrativemethod may include steps shown in connection with another illustrativemethod.

Apparatus may omit features shown and/or described in connection withillustrative apparatus. Embodiments may include features that areneither shown nor described in connection with the illustrativeapparatus. Features of illustrative apparatus may be combined. Forexample, an illustrative embodiment may include features shown inconnection with another illustrative embodiment.

The drawings show illustrative features of apparatus and methods inaccordance with the principles of the invention. The features areillustrated in the context of selected embodiments. It will beunderstood that features shown in connection with one of the embodimentsmay be practiced in accordance with the principles of the inventionalong with features shown in connection with another of the embodiments.

One of ordinary skill in the art will appreciate that the steps shownand described herein may be performed in other than the recited orderand that one or more steps illustrated may be optional. The methods ofthe above-referenced embodiments may involve the use of any suitableelements, steps, computer-executable instructions, or computer-readabledata structures. In this regard, other embodiments are disclosed hereinas well that can be partially or wholly implemented on acomputer-readable medium, for example, by storing computer-executableinstructions or modules or by utilizing computer-readable datastructures.

Thus, methods and systems for digital file recognition and deposit areprovided. Persons skilled in the art will appreciate that the presentinvention can be practiced by other than the described embodiments,which are presented for purposes of illustration rather than oflimitation, and that the present invention is limited only by the claimsthat follow.

What is claimed is:
 1. A digital file recognition and deposit system,said system comprising: a processor; and a non-transitory memory storingcomputer executable instructions that, when run on the processor, areconfigured to: receive, via email, an unidentified file comprising atleast one document image; extract metadata from the email, said metadatacomprising a sender of the email; automatically identify, based on thesender of the email and in conjunction with information stored in adatabase, a target client associated with the unidentified file;automatically identify, based on the target client and in conjunctionwith information stored in the database, at least one account linked tothe target client; extract the at least one document image from theunidentified file; and for each of the at least one document images:search a set of document templates for a matching document template thatsatisfies a threshold level of similarity to the document image, whereinsatisfying the threshold level of similarity to the document imagecomprises satisfying a predetermined mapping between the set of documenttemplates and a header on each document image, said header comprising abarcode and/or an alphanumeric document code; create a labeled file,said labeled file comprising the document image and a label identifyingthe labeled file based, at least in part, on the matching documenttemplate; select an account from the at least one account based, atleast in part, on a predetermined mapping between document types andaccount types, for depositing the labeled file; and deposit the labeledfile in the selected account; wherein, when the unidentified filecomprises one or more pages, the computer executable instructions arefurther configured to: segment the unidentified file into the one ormore pages; define each page as a document image; for each page of theone or more pages, execute the search for a matching document template,and create an identifier for the page based, at least in part, on thematching document template; group the one or more pages into uniformsets, each uniform set comprising one or more pages that have matchingidentifiers; for each uniform set that comprises more than one page,stitch the more than one page of the uniform set into a single documentimage; and perform the create, select, and deposit for each documentimage.
 2. The system of claim 1, wherein the barcode and/or alphanumericdocument code is extracted from the header using optical characterrecognition (“OCR”).
 3. The system of claim 1, wherein the computerexecutable instructions are further configured to extract data from thedocument image, and update a database with the data.
 4. The system ofclaim 1, wherein the set of document templates includes one or morecontractual forms, one or more financial forms, and/or one or moreidentification documents.
 5. The system of claim 1, wherein theunidentified file is received as an email attachment.
 6. The system ofclaim 1, wherein the system is configured to operate as an email plugin.7. The system of claim 1, further configured to be operable withunidentified files of the following file formats: pdf, png, tif, jpg,jpeg, gif, and pnp.
 8. The system of claim 1, further configured to beoperable when one or more of the at least one account is a prospectiveaccount, and wherein the at least one account includes one or more of alist of account types comprising: trust, investment, custody, estate,and banking.